Re: Deploying independently versioned modules

[Charles Honton]

Take a look at maven exists plugin 
[https://chonton.github.io/exists-maven-plugin/0.0.2/ 
].  This has goals to 
prevent deployment or installation of artifacts which already exist.

> On Feb 5, 2017, at 5:38 AM, org.apache.maven.u...@io7m.com wrote:
> 
> Hello.
> 
> For years, I've been developing libraries as sets of modules sharing a
> (semantic) version number. For each project, the project's root Maven
> module defines the version number for all modules in the project. As a
> result, intra-project dependencies can be efficiently declared like
> this:
> 
>  
>${project.groupId}
>a-module
>${project.version}
>  
> 
> My release process for version x.y.z of any project looks like this:
> 
>  $ git flow release start x.y.z
>  $ mvn versions:set -DnewVersion=x.y.z
>  $ git add pom.xml */pom.xml
>  $ git commit -m 'Mark x.y.z'
>  (try a build, wait for CI results, etc, etc, etc)
>  $ git flow release finish
>  $ git push --all
>  $ git push --tags
>  $ mvn clean deploy site site:stage && mvn nexus-staging:rc-list
>  $ mvn nexus-staging:rc-close -DstagingRepositoryId=...
>  $ mvn nexus-staging:rc-release -DstagingRepositoryId=...
> 
> However, I've recently begun migrating to OSGi and in an OSGi context,
> as soon as you have API bundles, it makes more sense to have
> independently semantically-versioned modules. The version number of the
> aggregating root Maven module therefore identifies a set of module
> versions as opposed to dictating a fixed version number for all
> submodules.
> 
> This is all fine, except for step 8 in my release process... If an API
> module has not changed, the version number will not have changed.
> Artifacts are immutable, and therefore I don't want to attempt to
> deploy the same version of a module again. I can try to manually deploy
> by specifying a list of projects with -pl, but this means that my
> release process has to be different for each project. I have rather a
> lot of projects (~70 and counting), so I'd prefer to avoid any
> project-specific procedures in order to preserve my own sanity.
> 
> Is there some way I can get the deploy plugin (or possibly the nexus
> staging plugin) to determine that it doesn't need to deploy a module
> twice?
> 
> M

FINAL REMINDER: CFP for ApacheCon closes February 11th

[Rich Bowen]

Dear Apache Enthusiast,

This is your FINAL reminder that the Call for Papers (CFP) for ApacheCon
Miami is closing this weekend - February 11th. This is your final
opportunity to submit a talk for consideration at this event.

This year, we are running several mini conferences in conjunction with
the main event, so if you're submitting for one of those events, please
pay attention to the instructions below.

Apache: Big Data
* Event information:
http://events.linuxfoundation.org/events/apache-big-data-north-america
* CFP:
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp

Apache: IoT (Internet of Things)
* Event Information: http://us.apacheiot.org/
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'IoT' in the Target Audience field)

CloudStack Collaboration Conference
* Event information: http://us.cloudstackcollab.org/
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'CloudStack' in the Target Audience field)

FlexJS Summit
* Event information - http://us.apacheflexjs.org/
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'Flex' in the Target Audience field)

TomcatCon
* Event information - https://tomcat.apache.org/conference.html
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'Tomcat' in the Target Audience field)

All other topics and projects
* Event information -
http://events.linuxfoundation.org/events/apachecon-north-america/program/about
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp

Admission to any of these events also grants you access to all of the
others.

Thanks, and we look forward to seeing you in Miami!

-- 
Rich Bowen
VP Conferences, Apache Software Foundation
rbo...@apache.org
Twitter: @apachecon



(You are receiving this email because you are subscribed to a dev@ or
users@ list of some Apache Software Foundation project. If you do not
wish to receive email from these lists any more, you must follow that
list's unsubscription procedure. View the headers of this message for
unsubscription instructions.)

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org