[jira] Created: (MNG-4846) Profile activated accidentially
Profile activated accidentially
---
Key: MNG-4846
URL: http://jira.codehaus.org/browse/MNG-4846
Project: Maven 2 & 3
Issue Type: Bug
Components: Profiles
Affects Versions: 2.2.1
Reporter: Maik Richey
Priority: Critical
When you define a profile activated like
{code}
...
someCase
false
somePropertyName
!Value
...
...
{code}
this profile will also be activated when no property/profile is defined on the
command line. I expected that profile beeing activated only when you supply
-DsomePropertyName=NotTheValue.
--
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-4848) finalName not taken into account for attached assemblies
finalName not taken into account for attached assemblies
Key: MNG-4848
URL: http://jira.codehaus.org/browse/MNG-4848
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Maik Richey
I got a multimodule POM here building two assemblies (jars) attached to the
project. Whatever I define in
{code}
...
[The name I want it to be]
...
{code}
is ignored. In the end of the day I'm not able to define the final name of the
artifacts?!
--
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-4846) Profile activated accidentially
[
http://jira.codehaus.org/browse/MNG-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237373#action_237373
]
Maik Richey commented on MNG-4846:
--
But then there is no difference to
{code}
...
false
!somePropertyName
...
{code}
and make no sense for me.
By specifying somePropertyName I would expect that property being
there but not having the value "Value". That makes the difference.
To be more precise:
What I would like to do is defining some properties as default. The same
properties should be used when activating a profile by property "env" and the
value "target". Different properties should be used - and are defined in
another profile - when specifying the property "env" with a value other than
"target" to activate that profile. So the only way, rather than creating a
profile for each possible value, is the way I tried to manage it and that's the
way how it should work in my opinion.
> Profile activated accidentially
> ---
>
> Key: MNG-4846
> URL: http://jira.codehaus.org/browse/MNG-4846
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
>Reporter: Maik Richey
>Assignee: Benjamin Bentmann
>Priority: Critical
>
> When you define a profile activated like
> {code}
> ...
>
>
> someCase
>
> false
>
> somePropertyName
> !Value
>
>
> ...
>
>
> ...
> {code}
> this profile will also be activated when no property/profile is defined on
> the command line. I expected that profile beeing activated only when you
> supply -DsomePropertyName=NotTheValue.
--
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] Reopened: (MNG-4846) Profile activated accidentially
[
http://jira.codehaus.org/browse/MNG-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maik Richey reopened MNG-4846:
--
see my last comment
> Profile activated accidentially
> ---
>
> Key: MNG-4846
> URL: http://jira.codehaus.org/browse/MNG-4846
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
>Reporter: Maik Richey
>Assignee: Benjamin Bentmann
>Priority: Critical
>
> When you define a profile activated like
> {code}
> ...
>
>
> someCase
>
> false
>
> somePropertyName
> !Value
>
>
> ...
>
>
> ...
> {code}
> this profile will also be activated when no property/profile is defined on
> the command line. I expected that profile beeing activated only when you
> supply -DsomePropertyName=NotTheValue.
--
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: (MASSEMBLY-508) finalName not taken into account for attached assemblies
[
http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237365#action_237365
]
Maik Richey commented on MASSEMBLY-508:
---
So there is no way to change the final name as it is stored on the local/remote
repo, right?
Alrigt, then I misunderstood the information found about the .
Sorry.
> finalName not taken into account for attached assemblies
>
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the
> project. Whatever I define in
> {code}
>
> ...
> [The name I want it to be]
> ...
>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of
> the artifacts?!
--
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: (MASSEMBLY-508) finalName not taken into account for attached assemblies
[
http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237365#action_237365
]
Maik Richey edited comment on MASSEMBLY-508 at 10/4/10 4:35 AM:
So there is no way to change the final name as it is stored on the local/remote
repo, right?
Alright, then I misunderstood the information found about the .
Sorry.
was (Author: compi):
So there is no way to change the final name as it is stored on the
local/remote repo, right?
Alrigt, then I misunderstood the information found about the .
Sorry.
> finalName not taken into account for attached assemblies
>
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the
> project. Whatever I define in
> {code}
>
> ...
> [The name I want it to be]
> ...
>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of
> the artifacts?!
--
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] Updated: (MNG-4846) Profile activated accidentially
[
http://jira.codehaus.org/browse/MNG-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maik Richey updated MNG-4846:
-
Attachment: SystemPropertyProfileActivator.patch
Created and attached a patch for SystemPropertyProfileActivator covering the
difference mentioned. Please check it and give some feedback.
> Profile activated accidentially
> ---
>
> Key: MNG-4846
> URL: http://jira.codehaus.org/browse/MNG-4846
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
>Reporter: Maik Richey
>Assignee: Benjamin Bentmann
>Priority: Critical
> Attachments: SystemPropertyProfileActivator.patch
>
>
> When you define a profile activated like
> {code}
> ...
>
>
> someCase
>
> false
>
> somePropertyName
> !Value
>
>
> ...
>
>
> ...
> {code}
> this profile will also be activated when no property/profile is defined on
> the command line. I expected that profile beeing activated only when you
> supply -DsomePropertyName=NotTheValue.
--
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: (MCLEAN-46) Enable useDefaultExcludes per Fileset
Enable useDefaultExcludes per Fileset - Key: MCLEAN-46 URL: http://jira.codehaus.org/browse/MCLEAN-46 Project: Maven 2.x Clean Plugin Issue Type: Improvement Affects Versions: 2.4.1 Reporter: Maik Richey Attachments: useDefaultExcludes.patch Needed to clean some source folders from generated classes. So I added a profile for doing that and found that my .svn directories are gone as well. By looking at the code I discovered that usage of was almost implemented. So, I did the rest (see patch attached). -- 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: (MASSEMBLY-528) FileSet does not support filtering (again)
FileSet does not support filtering (again) -- Key: MASSEMBLY-528 URL: http://jira.codehaus.org/browse/MASSEMBLY-528 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Maik Richey Priority: Critical After switching to version 2.2 of the Assembly Plugin filtering for FileSets does not work again as in versions prior to 2.2-beta-3. Can anybody confirm this issue? -- 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
