10:39 a.m.
Mircea Markus created ISPN-2252:
-----------------------------------
Summary: mvn deploy -Pdistribution doesn't uploads the sources
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that is
it only activates a profile if there's no other profile in the same file explicitly or
implicitly active[1]
[1]
{quote}
... This profile will automatically be active for all builds unless another profile in the
same POM is activated using one of the previously described methods. All profiles that are
active by default are automatically deactivated when a profile in the POM is activated on
the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:41 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2252:
--------------------------------
Description:
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that is
it only activates a profile if there's no other profile in the same file explicitly or
implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in place
to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into the
preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in the
same POM is activated using one of the previously described methods. All profiles that are
active by default are automatically deactivated when a profile in the POM is activated on
the command line or through its activation config. ...
{quote}
was:
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that is
it only activates a profile if there's no other profile in the same file explicitly or
implicitly active[1]
[1]
{quote}
... This profile will automatically be active for all builds unless another profile in the
same POM is activated using one of the previously described methods. All profiles that are
active by default are automatically deactivated when a profile in the POM is activated on
the command line or through its activation config. ...
{quote}
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:28 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2252:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1275
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:32 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
Why is this suddenly an issue? I've been doing Infinispan releases for months without
any issues, such as:
https://repository.jboss.org/nexus/content/groups/public/org/infinispan/i...
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2252:
-------------------------------------
5.2.0.ALPHA2 is the only release performed post ISPN-1959(which modified the xml), but
indeed it worked on your release from the 20 July.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2252:
-------------------------------------
I've run the same sequence of commands as our release script:
"mvn clean"
"mvn install -Pjmxdoc -Dmaven.test.skip.exec=true" //this generates the sources
"mvn deploy -Pdistribution -Dmaven.test.skip.exec=true" // sources are not
uploaded at this step, please check(and close) my release on nexus[1]
Mind give it a spin on your local machine as well?
[mircea:~/github/u_ispn ]$ mvn --version
Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000)
Maven home: /Users/mircea/java/apache-maven-3.0.4
Java version: 1.6.0_33, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_33-b03-424.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.4", arch: "x86_64",
family: "mac"
[1] https://repository.jboss.org/nexus/index.html#stagingRepositories
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
I've replicated the issue and I see the same thing. The only thing I've changed
locally from alpha2 is to go from Maven 3.0.3 to Maven 3.0.4. That might have an impact.
I'll give it a shot with Maven 3.0.3.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:37 p.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
Hmmmm, the same issue happens with 3.0.3. This is really odd... I'm looking into it
further.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:57 p.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2252:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:34 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Adrian Nistor reopened ISPN-2252:
---------------------------------
The current fix has the net effect of completely disabling generation of
runtime-classpath.txt for submodules (consequently, the demos from the distribution no
longer work in 5.2.0.alpha4). No submodule is child of root pom. The stuff we moved to
root has no effect on our submodules, so we should move it back. To get the sources jars
generated we should activate the 'extras' profile manually
(-Pdistribution,extras). There is no sane way to circumvent the way activeByDefault works
(by design) in maven. We could though merge distribution and extras profile if they are
always used together. Wdyt?
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:40 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Adrian Nistor reassigned ISPN-2252:
-----------------------------------
Assignee: Adrian Nistor (was: Mircea Markus)
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
@Adrian, possibly... what puzzles me here is what the change has been from alpha2 to
alpha3 that has brought this up. We never used to run the release with 'extras'
profile on. I was happy to skip this, but I think it's crucial that we understand
what's brought this in. Could you look into it?
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
Btw, util.py has not really changed. And the parent/pom.xml has had minimal changes really
since alpha2. Maybe the surefire upgrade is making things play up somehow?
Shouldn't... And we had your changes to reduce distribution size already in alpha2
(https://github.com/infinispan/infinispan/commits/5.2.0.ALPHA2).
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:03 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-2252:
-------------------------------------
I tried this on both 5.2.0.ALPHA1 and 5.2.0.ALPHA2 with maven 3.0.4 and 3.0.3 (it seems
maven version is irrelevant). The attached src jars are properly created when running
'mvn clean install -Pdistribution' on ALPHA1 but not on ALPHA2, so it seems the
issue is a side effect of pom changes from ISPN-1959 (distribution reduction). But this is
not a bug we need solve, it's just the way activeByDefault works when there are
multiple profiles defined at the same level and one of them is manually activated
(distribution). So the 'extras' profile has to be activated explicitly now. I will
add the 'extras' to the command line in the release scripts.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Adrian Nistor updated ISPN-2252:
--------------------------------
Status: Pull Request Sent (was: Reopened)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1293 (was:
https://github.com/infinispan/infinispan/pull/1275)
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2252:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2252:
-------------------------------------
[~galderz] re: "We never used to run the release with 'extras' profile
on." <-- extras was marked as "activeByDefault" which means so it kicked
in without explicitly enabling it.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:14 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
@Mircea, I know, but my point is that for Alpha2, which included ISPN-1959, I didn't
need to explicitly enable extras, and source jars were generated just fine :). Anyway,
let's not dwell on this. The fix is good to get us moving forward.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:50 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
@Mircea, I know, but my point is that for Alpha2, which included ISPN-1959, I didn't
need to explicitly enable extras, and source jars were generated just fine :). Anyway,
let's not dwell on this. The fix is good to get us moving forward.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:50 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2252:
----------------------------------------
@Mircea, I know, but my point is that for Alpha2, which included ISPN-1959, I didn't
need to explicitly enable extras, and source jars were generated just fine :). Anyway,
let's not dwell on this. The fix is good to get us moving forward.
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:52 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2252:
-----------------------------------
Comment: was deleted
(was: @Mircea, I know, but my point is that for Alpha2, which included ISPN-1959, I
didn't need to explicitly enable extras, and source jars were generated just fine :).
Anyway, let's not dwell on this. The fix is good to get us moving forward.)
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:52 a.m.
[
https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2252:
-----------------------------------
Comment: was deleted
(was: @Mircea, I know, but my point is that for Alpha2, which included ISPN-1959, I
didn't need to explicitly enable extras, and source jars were generated just fine :).
Anyway, let's not dwell on this. The fix is good to get us moving forward.)
mvn deploy -Pdistribution doesn't uploads the sources
-----------------------------------------------------
Key: ISPN-2252
URL: https://issues.jboss.org/browse/ISPN-2252
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Adrian Nistor
Fix For: 5.2.0.Alpha4
Here's why:
- the "distribution" which we use for releasing which was initially present in
root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
- the sources to be uploaded were generated by an "activeByDefault" profile
located in "parent/pom.xml", named "extras"
- the "activeByDefault" configuration has a rather error prone semantic, that
is it only activates a profile if there's no other profile in the same file explicitly
or implicitly active[1]
- not having the source is a show stopper for releasing as nexus has a validation in
place to check for sources (a good thing).
The solution is to merge the "distribution" profile from parent\pom.xml into
the preexisting one from root. This would allow the "extras" to kick in as there
isn't any other active profile in parent\pom.xml (at least when running
-Pdistribution).
[1] from mvn documentation
{quote}
... This profile will automatically be active for all builds unless another profile in
the same POM is activated using one of the previously described methods. All profiles that
are active by default are automatically deactivated when a profile in the POM is activated
on the command line or through its activation config. ...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4244
days inactive
4253
days old
infinispan-issues@lists.jboss.org
21 comments
3 participants
participants (3)
-
Adrian Nistor (JIRA) -
Galder Zamarreño (JIRA)
-
Mircea Markus (JIRA)