[
http://jira.codehaus.org/browse/MNG-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-4299.
-----------------------------
Resolution: Not A Bug
I'm not sure but I think NetBeans is on a very old embedder. You would need to
reproduce the behaviour on the command line to file a bug here.
> dependency profile activation
> -----------------------------
>
> Key: MNG-4299
> URL: http://jira.codehaus.org/browse/MNG-4299
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Embedding
> Affects Versions: 2.0.10, 2.1.0-M1, 2.1.0, 2.2.0, 2.2.1, 3.0-alpha-2
> Reporter: Vadim Khusainov
>
> I'm trying to understand problem which i met using netbeans. We are preparing
> some artifacts with different profiles. And profiles have their own
> dependencies. For example, some dependencies may become optional (if we are
> preparing osgi bundles with embedded dependencies) or version may change.
> Profiles get activated by properties.
> Some other projects use these artifacts as dependencies. And the only way to
> activate some specific profile of dependency is to specify property.
> If I'm doing dependency:tree from command line - everything works fine.
> Dependency plugin shows correct dependency tree (depending if I set some
> property or not). But if I'm using embedder (as netbeans does) - setting
> property does nothing. The profile of dependency doesn't get activated, it's
> just using default profile dependencies and dependencies not in profile.
--
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
