extracting in generated-source didn't work but in classes did!
So I was wrong ;)
the approach seems weird but let's see how it goes
--
View this message in context:
http://maven.40175.n5.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp215077p5773435.html
Sen
> @Manfred We cannot extract the jar into target/classes because the compile
> phase will not pick anything from target/classes but use that as output
> only. (I didn't check that but It makes sense :) )
>
> @Jorg I cannot let the user set the dependency "jar" in the pom.
> 1° the extracted path i
Hi Benoit,
Benoit Billington wrote:
> @Manfred We cannot extract the jar into target/classes because the compile
> phase will not pick anything from target/classes but use that as output
> only. (I didn't check that but It makes sense :) )
Try to extract the jar and "generated sources" add that
th is different for every aar dependency
2° android-maven-plugin should do it for the user as he only need to declare
the aar in the pom
3° the aar cannot be provided as it needs to be packaged into the apk
--
View this message in context:
http://maven.40175.n5.nabble.com/Programmatically-addi
Manfred Moser wrote:
>> Benoit Billington wrote:
>>
>>> I'm facing this problem too.
>>>
>>> Android has created a new format for its libraries called Android
>>> Archive
>>> (.aar)
>>>
>>> This format described here:
>>> http://tools.android.com/tech-docs/new-build-system/aar-format contains
>>>
> Benoit Billington wrote:
>
>> I'm facing this problem too.
>>
>> Android has created a new format for its libraries called Android
>> Archive
>> (.aar)
>>
>> This format described here:
>> http://tools.android.com/tech-docs/new-build-system/aar-format contains
>> a
>> "/classes.jar"
>>
>> How wou
Benoit Billington wrote:
> I'm facing this problem too.
>
> Android has created a new format for its libraries called Android Archive
> (.aar)
>
> This format described here:
> http://tools.android.com/tech-docs/new-build-system/aar-format contains a
> "/classes.jar"
>
> How would I be able to
Cheers
--
View this message in context:
http://maven.40175.n5.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp215077p5773206.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsub
endency first in the list.
Creates a new file pom2.xml with the new dependency (this can be changed to
overwrite the original file using: pom.xml > pom.xml
--
View this message in context:
http://maven.40175.n5.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp215077p577
ld to add the dependencies to the pom.xml. A more visible
workaround, if
you may.
Regards,
Costin.
--
View this message in context:
http://www.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp21173440p21681478.html
Sent from the Maven Developers mailing list archive
e
please point out what I'm doing wrong?
--
View this message in context:
http://www.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp21173440p21680711.html
Sent from the Maven Developers mailing list a
the other way around: run something before the
build to add the dependencies to the pom.xml. A more visible workaround, if
you may.
Regards,
Costin.
--
View this message in context:
http://www.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp21173440p216
Hi,
i also had this problem, and yes Jason is right don't do it! You will
have all sorts of follow up problems (like some other plugins not
working). It will work for the normal stuff, but be sure to start your
plugin in the validate phase.
Now i use a custom repository layout / repository t
add the inside dependencies, I just
want to add eclipse.jar (like Eclipse itself does during plugin
development).
I think this is a legitimate use case, *so*, for my use case, could anyone
please point out what I'm doing wrong?
--
View this message in context:
http://www.nabble.com/P
The alpha-2 will be released when we get the last couple issues done.
As for the final release date, no idea yet.
On 26-Jan-09, at 12:53 PM, Tom Huybrechts wrote:
On Mon, Jan 26, 2009 at 9:23 PM, Maarten Storm
wrote:
Yes it is a bad idea to add add dependencies programatically, I had a
RTF
On Mon, Jan 26, 2009 at 9:23 PM, Maarten Storm wrote:
> Yes it is a bad idea to add add dependencies programatically, I had a
> RTFM thing :-( . The Pom must be the project model in all cases. Oeps
> and sorry for that. I fixed the issue by using the scope import stated
> somewhere in the conversa
thod.java:585)
>>at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>at
>> org.codehaus.classworlds.Launcher.mainWithExitCo
ssage in context:
http://www.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp21173440p21664740.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr.
--
View this message in context:
http://www.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp21173440p21664740.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
Yes, that is what I'm looking for I think. I will give it a go in the
coming week.
On Sat, Dec 27, 2008 at 1:36 AM, Maarten Storm wrote:
> Yes I can add the dependencies using import (did not know that this
> was a scope...) and no, that is not possible since all the parent
> poms are poms that
Yes I can add the dependencies using import (did not know that this
was a scope...) and no, that is not possible since all the parent
poms are poms that have packaging pom, maven does not except these. I
try to fool Maven by adding a empty jar per pom and that worked, but
thats not the good way (f
On Dec 26, 2008, at 4:11 PM, Maarten Storm wrote:
Hello,
The reason why I would like to add dependencies programmaticaly is the
following: In my open source project I have 3 subprojects that do not
share the same parent pom. I'm working on a new packaging strategy
called dpom. This Dependency P
Can't you achieve this using the import scope? This would allow you to
declare the dependencyManagement of all your jars in one pom and effectively
import that into the projects that need it, thus synchronizing the
dependencies across them all.
On 12/26/08 7:11 PM, "Maarten Storm" wrote:
> Hell
Hello,
The reason why I would like to add dependencies programmaticaly is the
following: In my open source project I have 3 subprojects that do not
share the same parent pom. I'm working on a new packaging strategy
called dpom. This Dependency Pom is just like a normal pom but it
synchronized proje
From the Maven 1.x days where we did this and realized that if the
model of your dependencies not explicit in your pom.xml file then it's
not clear to anyone where dependencies are coming from and leads to
problems.
On 24-Dec-08, at 6:53 PM, Maarten Storm wrote:
Hello all,
I would like to
don't do that. Among other things it will mess up the IDE integration.
The project model shall be declarative.
Milos
On Fri, Dec 26, 2008 at 6:08 PM, Ralph Goers wrote:
> Under certain circumstances this could be done but I would need to
> understand the use case to tell you how.
>
> On Dec 24,
Under certain circumstances this could be done but I would need to
understand the use case to tell you how.
On Dec 24, 2008, at 3:53 PM, Maarten Storm wrote:
Hello all,
I would like to add programmatically dependencies to the MavenProject.
I have looked in the mail archives but I could not fi
Hello all,
I would like to add programmatically dependencies to the MavenProject.
I have looked in the mail archives but I could not find info on this
topic.Is there a possible solution for this?
Kind regards,
Maarten Storm
-
To
28 matches
Mail list logo
