Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add HttpPitMinter IT #639

Closed
wants to merge 4 commits into from
Closed

Add HttpPitMinter IT #639

wants to merge 4 commits into from

Conversation

osmandin
Copy link
Contributor

assertEquals(pid, "baz");
}

private String startServer(final String data) throws IOException {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason you are not using the standard Grizzly startup pattern? I am a little concerned about port conflicts when running this with other services, i.e. not using build-helper-maven-plugin

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, the test is starting Grizzly with PortRange, which does the same job of port reservation and assignment as builder-helper-maven-plugin (or so it seems to me). I could definitely increase the number of ports to try, though.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with the rest of the Fedora codebase, please use the build-helper-maven-plugin for test port management.

*/
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration("/spring-test/test-container.xml")
public class HttpPidMinterIT {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test class should be in fcrepo-kernel-impl, not fcrepo-http-api.

</dependency>
<dependency>
<groupId>org.glassfish.jersey.core</groupId>
<artifactId>jersey-server</artifactId>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be: <scope>test</scope>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of adding these dependencies to -kernel-impl, why not yank the HttpPidMinter out into a separate module? I'm a little worried doing this will a) give people the wrong idea about -kernel, and b) make it harder to detect accidental inclusion of HTTP-specific behavior that this level (which really, really shouldn't care about HTTP)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't believe I didn't notice this! What on Earth is a class named HttpPidMinter doing in -kernel-impl? +1 to what @cbeer says and -1 to @fedoradmin for putting this class in here.

@awoods
Copy link

awoods commented Nov 17, 2014

Resolved with: cd2d11c

@awoods awoods closed this Nov 17, 2014
awoods referenced this pull request in osmandin/fcrepo4 Nov 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants