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

#12: provide initial version of top-level pom for EE4J projects #13

Merged
merged 3 commits into from Apr 18, 2018

Conversation

lukasj
Copy link
Member

@lukasj lukasj commented Apr 17, 2018

Signed-off-by: Lukas Jungmann lukas.jungmann@oracle.com

…ojects

Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
Copy link
Member

@m0mus m0mus left a comment

Choose a reason for hiding this comment

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

LGTM

parent/pom.xml Outdated
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.eclipse.jakartaee</groupId>
Copy link
Member

Choose a reason for hiding this comment

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

Is this something that should be run through the Jakarta EE WG?
The groupId here should match the groupId for future specifications.

Copy link
Member

Choose a reason for hiding this comment

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

I would say that it should be org.eclipse.ee4j and match groupid for future implementations. Subprojects can override it anyway.

Copy link
Member

Choose a reason for hiding this comment

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

I agree, org.eclipse.ee4j sounds much better. We should leave the jakarta name out for ee4j projects.

Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
@lukasj
Copy link
Member Author

lukasj commented Apr 17, 2018

change gId to org.eclipse.ee4j in 736750c

parent/pom.xml Outdated
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>

<name>Jakarta EE Project</name>

Choose a reason for hiding this comment

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

Should this say EE4J project?

Copy link
Member

Choose a reason for hiding this comment

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

Good catch! Yes, it should...

Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
@lukasj
Copy link
Member Author

lukasj commented Apr 17, 2018

fixed project name in 67d408f

@m0mus m0mus merged commit c7386d7 into eclipse-ee4j:master Apr 18, 2018
@m0mus
Copy link
Member

m0mus commented Apr 18, 2018

Merged. @lukasj, you can proceed and deploy it to Maven Central.

@lukasj lukasj deleted the parent_pom branch April 18, 2018 17:20
@lukasj
Copy link
Member Author

lukasj commented Apr 18, 2018

@m0mus - it's not that simple as I'm not owner of eclipse.org. I also don't have write access to this git repo which is needed nor to the implied staging repo. Let's start with #14

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