[jira] Commented: (MNG-4565) Multiple profile activation conditions does not work
[
http://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222462#action_222462
]
Clemens Fuchslocher commented on MNG-4565:
--
[POM Reference|http://maven.apache.org/pom.html#Activation]:
{quote}
Activation occurs when one or more of the specified criteria have been met.
When the first positive result is encountered, processing stops and the profile
is marked as active.
{quote}
Not really useful.
> Multiple profile activation conditions does not work
>
>
> Key: MNG-4565
> URL: http://jira.codehaus.org/browse/MNG-4565
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
> Environment: All platforms.
>Reporter: Nicholas Allen
>
> According to the documentation at
> http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html
> a profile is activated when all activation conditions are met (which makes
> sense of course). But when I try to use this it does not work. It seems maven
> does an OR instead of an AND (which is not rearly as useful and is the
> opposite of what the documentation says at the previous link).
> For example, if I have one profile that is activated like this:
>
> false
>
>linux
>
>
> and another profile that is activated like this:
>
> false
>
>linux
>
>
> release
> true
>
>
> Then I would expect the second profile to only be activated if the OS is
> linux and the release property is defined.
> When I run 'mvn help:active-profiles' however, maven shows that both profiles
> are active even though the release property is not defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4565) Multiple profile activation conditions does not work
[
http://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222465#action_222465
]
Clemens Fuchslocher commented on MNG-4565:
--
This was introduced by MNG-3106:
{quote}
The new behaviour is that the profile will be activated if any of the
activators returns true (i.e. an "or" operation).
{quote}
> Multiple profile activation conditions does not work
>
>
> Key: MNG-4565
> URL: http://jira.codehaus.org/browse/MNG-4565
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
> Environment: All platforms.
>Reporter: Nicholas Allen
>
> According to the documentation at
> http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html
> a profile is activated when all activation conditions are met (which makes
> sense of course). But when I try to use this it does not work. It seems maven
> does an OR instead of an AND (which is not rearly as useful and is the
> opposite of what the documentation says at the previous link).
> For example, if I have one profile that is activated like this:
>
> false
>
>linux
>
>
> and another profile that is activated like this:
>
> false
>
>linux
>
>
> release
> true
>
>
> Then I would expect the second profile to only be activated if the OS is
> linux and the release property is defined.
> When I run 'mvn help:active-profiles' however, maven shows that both profiles
> are active even though the release property is not defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4565) Multiple profile activation conditions does not work
[
http://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222468#action_222468
]
Clemens Fuchslocher commented on MNG-4565:
--
An and element would be useful:
{noformat}
false
linux
release
true
{noformat}
> Multiple profile activation conditions does not work
>
>
> Key: MNG-4565
> URL: http://jira.codehaus.org/browse/MNG-4565
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
> Environment: All platforms.
>Reporter: Nicholas Allen
>
> According to the documentation at
> http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html
> a profile is activated when all activation conditions are met (which makes
> sense of course). But when I try to use this it does not work. It seems maven
> does an OR instead of an AND (which is not rearly as useful and is the
> opposite of what the documentation says at the previous link).
> For example, if I have one profile that is activated like this:
>
> false
>
>linux
>
>
> and another profile that is activated like this:
>
> false
>
>linux
>
>
> release
> true
>
>
> Then I would expect the second profile to only be activated if the OS is
> linux and the release property is defined.
> When I run 'mvn help:active-profiles' however, maven shows that both profiles
> are active even though the release property is not defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4337) A default-activated profile in the profiles.xml file is not deactivated when another profile is activated explicitly
A default-activated profile in the profiles.xml file is not deactivated when
another profile is activated explicitly
Key: MNG-4337
URL: http://jira.codehaus.org/browse/MNG-4337
Project: Maven 2
Issue Type: Bug
Components: Profiles
Affects Versions: 2.2.1, 2.1.0, 2.0.10
Environment: Java 1.6.0, Debian GNU/Linux 5.0
Reporter: Clemens Fuchslocher
Attachments: profiles.tar.gz
The behavior of the activeByDefault element inside a POM is documented in
[Introduction to Build
Profiles|http://maven.apache.org/guides/introduction/introduction-to-profiles.html]:
{quote}
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}
And it also works this way:
{noformat}
$ tar -zxvf profiles.tar.gz
$ cd profiles/internal
$ mvn help:all-profiles
...
Profile Id: red (Active: true , Source: pom)
Profile Id: green (Active: false , Source: pom)
Profile Id: blue (Active: false , Source: pom)
...
$ mvn help:all-profiles -P blue
...
Profile Id: blue (Active: true , Source: pom)
Profile Id: red (Active: false , Source: pom)
Profile Id: green (Active: false , Source: pom)
...
$ mvn help:active-profiles
...
The following profiles are active:
- red (source: pom)
...
$ mvn help:active-profiles -P blue
...
The following profiles are active:
- blue (source: pom)
...
$ mvn help:effective-pom
...
red
...
$ mvn help:effective-pom -P blue
...
blue
...
{noformat}
But if the profiles are defined in the profiles.xml file, then the behavior of
the activeByDefault element is changed unexpectedly: The red profile and the
color property is always active and red:
{noformat}
$ tar -zxvf profiles.tar.gz
$ cd profiles/external
$ mvn help:all-profiles
...
Profile Id: red (Active: true , Source: profiles.xml)
Profile Id: green (Active: false , Source: profiles.xml)
Profile Id: blue (Active: false , Source: profiles.xml)
...
$ mvn help:all-profiles -P blue
...
Profile Id: blue (Active: true , Source: profiles.xml)
Profile Id: red (Active: true , Source: profiles.xml)
Profile Id: green (Active: false , Source: profiles.xml)
...
$ mvn help:active-profiles
...
The following profiles are active:
- red (source: profiles.xml)
...
$ mvn help:active-profiles -P blue
...
The following profiles are active:
- blue (source: profiles.xml)
- red (source: profiles.xml)
...
$ mvn help:effective-pom
...
red
...
$ mvn help:effective-pom -P blue
...
red
...
{noformat}
Principle of Least Surprise?
Maybe a bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-599) Broken link to j2ee-simple.tar.gz on multi-module-projects.html
Broken link to j2ee-simple.tar.gz on multi-module-projects.html
---
Key: MECLIPSE-599
URL: http://jira.codehaus.org/browse/MECLIPSE-599
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Plugin Documentation
Reporter: Clemens Fuchslocher
On [Using maven-eclipse-plugin in multi-module projects with
WTP|http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html]
is a broken link to the project archive j2ee-simple.tar.gz.
The archive is wrongly referenced as an anchor:
{noformat}
...
You can download it from here.
...
{noformat}
Removing the hash fixes the problem:
{noformat}
...
You can download it from here.
...
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MAVENUPLOAD-2598) Rsync for MySQL Connector/J broken somewhere
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190606#action_190606 ] Clemens Fuchslocher edited comment on MAVENUPLOAD-2598 at 9/11/09 6:51 AM: --- The rsync location for MySQL's remote repository is not listed in the sync.csv (https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/) file. If I understand the "Guide to uploading artifacts to the Central Repository" (http://maven.apache.org/guides/mini/guide-central-repository-upload.html) correctly, then this file contains all automatically synchronized repositories. was (Author: c): The rsync location for MySQL's remote repository is not listed in the sync.csv (https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/) file. If I understand the Guide to uploading artifacts to the Central Repository (http://maven.apache.org/guides/mini/guide-central-repository-upload.html) correctly, then this file contains all automatically synchronized repositories. > Rsync for MySQL Connector/J broken somewhere > > > Key: MAVENUPLOAD-2598 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2598 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Mark Matthews > > It seems that the rsync of the bundles that we (MySQL) put up to be > synchronized into the repository has broken somewhere. Are you receiving > errors on your end? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2598) Rsync for MySQL Connector/J broken somewhere
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190606#action_190606 ] Clemens Fuchslocher commented on MAVENUPLOAD-2598: -- The rsync location for MySQL's remote repository is not listed in the [sync.csv|https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/] file. If I understand the [Guide to uploading artifacts to the Central Repository|http://maven.apache.org/guides/mini/guide-central-repository-upload.html] correctly, then this file contains all automatically synchronized repositories. > Rsync for MySQL Connector/J broken somewhere > > > Key: MAVENUPLOAD-2598 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2598 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Mark Matthews > > It seems that the rsync of the bundles that we (MySQL) put up to be > synchronized into the repository has broken somewhere. Are you receiving > errors on your end? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MAVENUPLOAD-2598) Rsync for MySQL Connector/J broken somewhere
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190606#action_190606 ] Clemens Fuchslocher edited comment on MAVENUPLOAD-2598 at 9/11/09 6:50 AM: --- The rsync location for MySQL's remote repository is not listed in the sync.csv (https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/) file. If I understand the Guide to uploading artifacts to the Central Repository (http://maven.apache.org/guides/mini/guide-central-repository-upload.html) correctly, then this file contains all automatically synchronized repositories. was (Author: c): The rsync location for MySQL's remote repository is not listed in the [sync.csv|https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/] file. If I understand the [Guide to uploading artifacts to the Central Repository|http://maven.apache.org/guides/mini/guide-central-repository-upload.html] correctly, then this file contains all automatically synchronized repositories. > Rsync for MySQL Connector/J broken somewhere > > > Key: MAVENUPLOAD-2598 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2598 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Mark Matthews > > It seems that the rsync of the bundles that we (MySQL) put up to be > synchronized into the repository has broken somewhere. Are you receiving > errors on your end? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2598) Rsync for MySQL Connector/J broken somewhere
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191459#action_191459 ] Clemens Fuchslocher commented on MAVENUPLOAD-2598: -- I found this http://mail-archives.apache.org/mod_mbox/maven-repo-maintainers/200809.mbox/%3c1a5b6c410809080513v28ec6249vc3f3bb1601f25...@mail.gmail.com%3e mail on the repo-maintainers mailing list (http://mail-archives.apache.org/mod_mbox/maven-repo-maintainers/): "mysql and com.exadel.flamingo syncs have been removed due to permanent failure". http://mail-archives.apache.org/mod_mbox/maven-repo-maintainers/200808.mbox/%3c19456522.01220003190581.javamail.ma...@sonatype03.managed.contegix.com%3e http://mail-archives.apache.org/mod_mbox/maven-repo-maintainers/200809.mbox/%3c23105029.01220560663009.javamail.ma...@sonatype03.managed.contegix.com%3e http://mail-archives.apache.org/mod_mbox/maven-repo-maintainers/200809.mbox/%3c19456522.01220607929920.javamail.ma...@sonatype03.managed.contegix.com%3e Are the following settings still correct and working? "mysql","ma...@rsync.mysql.com:/web/sites/live/maven/mysql","rsync_ssh","Mark Matthews","m...@mysql.com",, Details are described in "Sync'ing your own repository to the central repository automatically" (http://maven.apache.org/guides/mini/guide-central-repository-upload.html#Syncing_your_own_repository_to_the_central_repository_automatically). > Rsync for MySQL Connector/J broken somewhere > > > Key: MAVENUPLOAD-2598 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2598 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Mark Matthews > > It seems that the rsync of the bundles that we (MySQL) put up to be > synchronized into the repository has broken somewhere. Are you receiving > errors on your end? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
