Thanks for your ideas.
I don't have any hope to see the JavaFX jars in Central..
So I will stick with the automated deployment into local repository.
Thanks,
Johannes
On 05/25/2010 07:13 PM, Manfred Moser wrote:
>>> That is not that easy. I depend on JavaFX jars. And it is additional
>>> work
>> That is not that easy. I depend on JavaFX jars. And it is additional
>> work to add those (that are about 15) to the repository for every
>> developer.
>> Setting a system property (javafx.home) is much easier
>
> The best solution is to get the JavaFX jars into Central or another
> Maven re
> That is not that easy. I depend on JavaFX jars. And it is additional
> work to add those (that are about 15) to the repository for every developer.
> Setting a system property (javafx.home) is much easier
The best solution is to get the JavaFX jars into Central or another
Maven repository. S
, 2010 9:22 AM
> To: users@maven.apache.org
> Subject: Re: POM is invalid...
>
> On 05/24/2010 07:21 PM, Wayne Fay wrote:
> >>> [DEBUG] For dependency Dependency {groupId=javafx,
> >>> artifactId=javafxc,
> >> version=1.3.0, type=jar}: system-scope
On 05/24/2010 07:21 PM, Wayne Fay wrote:
>>> [DEBUG] For dependency Dependency {groupId=javafx, artifactId=javafxc,
>> version=1.3.0, type=jar}: system-scoped dependency must specify an
>> absolute path systemPath.
>
> Don't use system scope and thus don't use systemPath.
That is not that easy. I
From: maili...@cedarsoft.com
> To: users@maven.apache.org
> Subject: POM is invalid...
>
> Hi,
>
> at the moment I try to mavenize JFXtras.
> Unfortunately I run into a major problem: When I add a dependency to one
> of my projects, I get that message:
>
> > [W
>> [DEBUG] For dependency Dependency {groupId=javafx, artifactId=javafxc,
> version=1.3.0, type=jar}: system-scoped dependency must specify an
> absolute path systemPath.
Don't use system scope and thus don't use systemPath.
Use mvn:install install-file to put the jar where it belongs in the
loca
Aaaah sorry guys.
Have been working too long today.
The log shows the problem (directly at my eyes, don't know why I didn't
see that):
> [DEBUG] For dependency Dependency {groupId=javafx, artifactId=javafxc,
version=1.3.0, type=jar}: system-scoped dependency must specify an
absolute path systemPa
Hi,
at the moment I try to mavenize JFXtras.
Unfortunately I run into a major problem: When I add a dependency to one
of my projects, I get that message:
> [WARNING] POM for
'org.jfxtras:jfxtras-common:pom:0.7-SNAPSHOT:compile' is invalid.
(Full log at http://pastebin.com/tguzrAgN)
And of cour
Hi Ellecer,
Just scanning through this thread I'm not sure if anyone has asked you to
run "mvn help:effective-pom" in the problem environment. Does that show the
correct variable substitution?
Brett
On Tue, Nov 24, 2009 at 5:39 PM, Ellecer Valencia wrote:
> Hi Other Brett,
>
> It's a similar p
Hi Other Brett,
It's a similar problem, except that the environment settings are
coming from the shell environment and not a setttings.xml
Ellecer
On Mon, Nov 23, 2009 at 6:16 PM, Brett Randall wrote:
> Hi Ellecer,
>
> Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148
Hi Ellecer,
Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148 ,
which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does that
fit your parent POM hierarchy?
Other Brett
On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia wrote:
> On Mon, Nov 23, 2009 at 11:1
On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter wrote:
> Did you also "export WL_HOME"?
>
> I tried something similar here and it works fine in 2.2.1.
>
> - Brett
Hi Brett,
I'd presume the environment variable being there means that's already
happened. =)
This entry is in .bashrc so I'm pretty s
Did you also "export WL_HOME"?
I tried something similar here and it works fine in 2.2.1.
- Brett
On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
> But that's exactly the problem - it *is* defined in the environment. :(
>
> $ls -l $WL_HOME/server/lib/webservices.jar
> -rwxr-xr-x. 1 dev dev
But that's exactly the problem - it *is* defined in the environment. :(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xm
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe
Hi Brian,
Could you please clarify what's actually "plain wrong" about it?
Going back to the example I posted:
com.sun
rt
1.5.0.11
system
${java.home}/lib/rt.jar
weblogic
weblogic
10.0
system
${env.WL_HOME}/server/lib/webl
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which
allowed it to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log
that :).
On Fri, Nov 20, 2009 at 2:59 PM, E
No, not my team. I think a more sensible fix is to just put the
weblogic jars in Artifactory, but it's in a pom that I don't have much
control over.
Maybe 2.2.2 will fix it. =)
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall wrote:
> http://jira.codehaus.org/browse/MNG-4379 ... or did your team l
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia wrote:
> Hi Brett,
>
> Thanks for the suggestion. I may have found the issue. Would it be this:
>
>
> Validation Errors:
> [DEBUG] For dependency Dependency {groupId=weblo
Hi Brett,
Thanks for the suggestion. I may have found the issue. Would it be this:
Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
[DEBUG] For managed dependen
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia wrote:
> Hi,
>
> How come when I try a build using Maven 2.2.1 I get multiple messages like
> this:
>
> "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is
> invalid.
>
> It
Hi,
How come when I try a build using Maven 2.2.1 I get multiple messages like this:
"[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build."
These errors weren't displaying when I was using Maven 2.0.1
23 matches
Mail list logo