[jira] [Commented] (MNG-1388) Transitive Dependencies in a profile are not used
[
https://issues.apache.org/jira/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786038#comment-16786038
]
Robert Scholte commented on MNG-1388:
-
[~divStar] download attached pom-file (optionally rename it)
{{mvn -f mng1388.pom verify}} succeeds building only A
{{mvn -f mng1388.pom verify -Psome-profile}} fails due to missing directories B
and C (which makes sense).
Profiled modules are recognized, so I don't the issue.
> Transitive Dependencies in a profile are not used
> -
>
> Key: MNG-1388
> URL: https://issues.apache.org/jira/browse/MNG-1388
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0
> Environment: Windows XP using Maven 2.0.
>Reporter: dbradicich
>Priority: Major
> Attachments: mng1388.pom
>
>
> I have a jar project file that defines a dependency inside a certain profile.
> If I then include that project inside of another war project, the
> dependencies defined in the jar project's profile isn't getting transferred
> over to the war.
> Ie we have this:
> A depends on SQL or Oracle depending on profile
> B depends on A.
> If sql profile is active, I would expect that when I build B, it pulls
> the transitive dependancy on sql from A.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-1388) Transitive Dependencies in a profile are not used
[
https://issues.apache.org/jira/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784624#comment-16784624
]
Igor Tykhyy commented on MNG-1388:
--
I'd also like to see this issue fixed (though I am not sure I could fix it
myself). I'd like profiles to apply to *not only dependencies*, but also
*child-modules* (specified under {{}}).
{{A}}
{{ - B (child-module)}}
{{ - C (child-module)}}
Doing
{code:java}
mvn clean install -Psome-profile
{code}
should apply the profile {{some-profile}} on *A* as well as on *B* and *C*,
running the profile in each module containing it.
At least for me it does not work - especially not if modules are stored in
profiles themselves (I only need some modules to be built in order to deploy
them; aggregator-project-packaging is set to _pom_).
> Transitive Dependencies in a profile are not used
> -
>
> Key: MNG-1388
> URL: https://issues.apache.org/jira/browse/MNG-1388
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0
> Environment: Windows XP using Maven 2.0.
>Reporter: dbradicich
>Priority: Major
>
> I have a jar project file that defines a dependency inside a certain profile.
> If I then include that project inside of another war project, the
> dependencies defined in the jar project's profile isn't getting transferred
> over to the war.
> Ie we have this:
> A depends on SQL or Oracle depending on profile
> B depends on A.
> If sql profile is active, I would expect that when I build B, it pulls
> the transitive dependancy on sql from A.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-1388) Transitive Dependencies in a profile are not used
[
https://issues.apache.org/jira/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610838#comment-16610838
]
Abhinay Agarwal commented on MNG-1388:
--
I am trying to upgrade a library to work with JDK 11. There are some
dependencies which are no longer a part of the JDK, so I introduced a profile
which would activate depending on the JDK and would take care of the missing
dependencies:
{code:java}
JDK 11
false
11
11-ea+24
org.openjfx
javafx-controls
${javafx.version}
org.openjfx
javafx-fxml
${javafx.version}
{code}
The profile works well when I try to compile and install the library with JDK
11.
But when I try to use the library as a dependency in another application, maven
is unable to resolve the transitive dependencies inside the profile. Is there a
workaround for this problem?
> Transitive Dependencies in a profile are not used
> -
>
> Key: MNG-1388
> URL: https://issues.apache.org/jira/browse/MNG-1388
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0
> Environment: Windows XP using Maven 2.0.
>Reporter: dbradicich
>Priority: Major
>
> I have a jar project file that defines a dependency inside a certain profile.
> If I then include that project inside of another war project, the
> dependencies defined in the jar project's profile isn't getting transferred
> over to the war.
> Ie we have this:
> A depends on SQL or Oracle depending on profile
> B depends on A.
> If sql profile is active, I would expect that when I build B, it pulls
> the transitive dependancy on sql from A.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Commented: (MNG-1388) Transitive Dependencies in a profile are not used
[ https://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=281933#comment-281933 ] Ivan Bondarenko commented on MNG-1388: -- We are also waiting for this bug solve (have issue similar to described in MNG-4985). We have a lot of modules, which form a hierarchy (3 or 4 levels). Modules can be built with classifiers (release, debug etc). When war project references these modules, transitive dependencies without any classifiers are used. In fact that makes classifier paradigm useless. Transitive Dependencies in a profile are not used - Key: MNG-1388 URL: https://jira.codehaus.org/browse/MNG-1388 Project: Maven 2 3 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Environment: Windows XP using Maven 2.0. Reporter: Damian Bradicich Fix For: Issues to be reviewed for 3.x I have a jar project file that defines a dependency inside a certain profile. If I then include that project inside of another war project, the dependencies defined in the jar project's profile isn't getting transferred over to the war. Ie we have this: A depends on SQL or Oracle depending on profile B depends on A. If sql profile is active, I would expect that when I build B, it pulls the transitive dependancy on sql from A. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1388) Transitive Dependencies in a profile are not used
[ http://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242815#action_242815 ] Benjamin Bentmann commented on MNG-1388: I second Milos' concern about clashing profile ids. I think the approach outlined by Paul in MNG-4531 is more appropriate. Transitive Dependencies in a profile are not used - Key: MNG-1388 URL: http://jira.codehaus.org/browse/MNG-1388 Project: Maven 2 3 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Environment: Windows XP using Maven 2.0. Reporter: Damian Bradicich Fix For: Issues to be reviewed for 3.x I have a jar project file that defines a dependency inside a certain profile. If I then include that project inside of another war project, the dependencies defined in the jar project's profile isn't getting transferred over to the war. Ie we have this: A depends on SQL or Oracle depending on profile B depends on A. If sql profile is active, I would expect that when I build B, it pulls the transitive dependancy on sql from A. -- 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-1388) Transitive Dependencies in a profile are not used
[
http://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=182802#action_182802
]
Rob ten Hove commented on MNG-1388:
---
I would not like limiting the scope of the dependency pom profile triggering to
the same groupId. I'm working on a very large project with a lot of groupId's.
The complete project can run on a middleware project or a stub of it. To
accomplish this, the data objects that the applications use to communicate with
the middleware will be either the 'real' implementations or the stubbed ones.
So for each data object we have two versions: impl and stub. To get the
right dependencies, each project that uses the data objects will have two
profiles, called impl and stub. Now if I want to build an application with
Maven, I will activate either profile. I just discovered that this does not
work with Maven right now!
So I have this situation regarding dependencies:
{noformat}
A
- B
- profile id=stub
- DO1_stub
- profile id=impl
- DO1_impl
B
- profile id=stub
- DO2_stub
- profile id=impl
- DO2_impl
{noformat}
If I run mvn -Pstub clean package on A's pom, then I will have DO1_stub but
*not* DO2_stub!
I think that the profile id problem should be solved by good naming
conventions, not by limiting the scope since that will reduce the applicability
a lot. For example if it is a local profile, prefix it with the artifactId. If
it is to be used within a group, prefix it with the groupId etc.
Transitive Dependencies in a profile are not used
-
Key: MNG-1388
URL: http://jira.codehaus.org/browse/MNG-1388
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0
Environment: Windows XP using Maven 2.0.
Reporter: Damian Bradicich
Fix For: 3.x
I have a jar project file that defines a dependency inside a certain profile.
If I then include that project inside of another war project, the
dependencies defined in the jar project's profile isn't getting transferred
over to the war.
Ie we have this:
A depends on SQL or Oracle depending on profile
B depends on A.
If sql profile is active, I would expect that when I build B, it pulls
the transitive dependancy on sql from A.
--
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-1388) Transitive Dependencies in a profile are not used
[
http://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=182825#action_182825
]
Rob ten Hove commented on MNG-1388:
---
Update: the situation described above does work when profile activation using
properties is used:
{noformat}
profile
idstub/id
activation
property
namestub/name
/property
/activation
...
/profile
{noformat}
Running mvn -Pstub -Dstub clean package on A's pom gives both DO1_stub *and*
DO2_stub.
Transitive Dependencies in a profile are not used
-
Key: MNG-1388
URL: http://jira.codehaus.org/browse/MNG-1388
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0
Environment: Windows XP using Maven 2.0.
Reporter: Damian Bradicich
Fix For: 3.x
I have a jar project file that defines a dependency inside a certain profile.
If I then include that project inside of another war project, the
dependencies defined in the jar project's profile isn't getting transferred
over to the war.
Ie we have this:
A depends on SQL or Oracle depending on profile
B depends on A.
If sql profile is active, I would expect that when I build B, it pulls
the transitive dependancy on sql from A.
--
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-1388) Transitive Dependencies in a profile are not used
[ http://jira.codehaus.org/browse/MNG-1388?page=comments#action_72448 ] Milos Kleint commented on MNG-1388: --- since profiles are identified by ids, it will probably happen that these IDs will clash in completely unrelated 3rd party libraries. maybe the scope of dependency pom profile triggering should be limuted to the same groupId? Transitive Dependencies in a profile are not used - Key: MNG-1388 URL: http://jira.codehaus.org/browse/MNG-1388 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Environment: Windows XP using Maven 2.0. Reporter: Damian Bradicich Fix For: 2.1 I have a jar project file that defines a dependency inside a certain profile. If I then include that project inside of another war project, the dependencies defined in the jar project's profile isn't getting transferred over to the war. Ie we have this: A depends on SQL or Oracle depending on profile B depends on A. If sql profile is active, I would expect that when I build B, it pulls the transitive dependancy on sql from A. -- 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
