versions in poms are messed up, so trunk won't build
----------------------------------------------------
Key: PAXLOGGING-67
URL: http://issues.ops4j.org/browse/PAXLOGGING-67
Project: Pax Logging
Issue Type: Bug
Reporter: David Jencks
Assignee: David Jencks
The way the release profile is set up to not build samples and it means that
the pom versions won't get updated in these module when you release. So, trunk
won't build now.
A better (IMO) way is to have the release profile skip deployment on these
modules. Then all the modules will be found and updated during release, but we
won't deploy the samples and it modules.
Versions are also spread all around the different projects.
Since my understanding of ops4j is that it is a do-ocracy I plan to commit my
changes to implement this... hoping for feedback if anything goes wrong.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
