Re: [ee4j-build] First working release job

[Tomas Kraus <tomas.kraus@xxxxxxxxxx>]

Each project can implement pom.xml and Jenkins jobs in its own way. I shared my script as an example and it's up to you if you use it with some modifications or not.
nexus-staging-maven-plugin is on my "nice to have tools" list. But with current deadline and number of jobs to implement it just has to stay there.

I don't know proper serverId and nexusUrl values.

Tomas

Dne 05/10/18 v 09:08 Tom Jenkinson napsal(a):

More specifically, if I would like to do something like the following, what would the serverId and nexusUrl be:

<plugin>
          <groupId>org.sonatype.plugins</groupId>
          <artifactId>nexus-staging-maven-plugin</artifactId>
          <version>1.6.8</version>
          <extensions>true</extensions>
          <configuration>
            <serverId>--------------
            <nexusUrl>--------------
            <autoReleaseAfterClose>true</autoReleaseAfterClose>
          </configuration>
</plugin>

If the artifact I deploy is a SNAPSHOT release, do I need to change anything
in the above mvn command?
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build