Re: Strange potential bug Maven2?

2011-05-29 Thread Yucca Nel
I refactored the dependency into a dependency management(all my 
dependencies), but I note that there is still going to be RException for the 
Faces Servlet as my IDE is already complaining that the Class is missing.
It's no problem though as I can just revert to what works, but would be nice 
to have my own Majorra pom and an alternate MyFaces pom for the different 
types of containers.


Please inform (if you can) if this is an IDE or Maven issue?

-Original Message- 
From: Yucca Nel

Sent: Sunday, May 29, 2011 12:45 PM
To: Maven Users List
Subject: Re: Strange potential bug Maven2?

Many thanks. I am reading a oreilly Sonatype Maven and such valuable info
not included :D

-Original Message- 
From: Hilco Wijbenga

Sent: Saturday, May 28, 2011 9:57 PM
To: Maven Users List
Subject: Re: Strange potential bug Maven2?

On 28 May 2011 07:09, Yucca Nel  wrote:

Sorry, I will try be clearer... this:


  com.sun.faces
  jsf-api
  2.0.3
  compile
  
  
  com.sun.faces
  jsf-impl
  2.0.3
  compile
  

Is not the same as this:


  org.thejarbar
  hib-jsf-jta-dep
  pom
  1.0
  
===
The pom project:
===

http://maven.apache.org/POM/4.0.0";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
  4.0.0

  org.thejarbar
  facelets-dep
  1.0
  pom

  
  
  
  com.sun.faces
  jsf-api
  2.0.3
  compile
  
  
  com.sun.faces
  jsf-impl
  2.0.3
  compile
  
  
  



I was under the impression that the two are identical?


You should add import. Just having the dependency means
it's available at compile time which is not of any help to you.

Note, though, that scope import is quite limited. It only works in the
dependencyManagement section. See
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Strange potential bug Maven2?

2011-05-29 Thread Yucca Nel
Many thanks. I am reading a oreilly Sonatype Maven and such valuable info 
not included :D


-Original Message- 
From: Hilco Wijbenga

Sent: Saturday, May 28, 2011 9:57 PM
To: Maven Users List
Subject: Re: Strange potential bug Maven2?

On 28 May 2011 07:09, Yucca Nel  wrote:

Sorry, I will try be clearer... this:


  com.sun.faces
  jsf-api
  2.0.3
  compile
  
  
  com.sun.faces
  jsf-impl
  2.0.3
  compile
  

Is not the same as this:


  org.thejarbar
  hib-jsf-jta-dep
  pom
  1.0
  
===
The pom project:
===

http://maven.apache.org/POM/4.0.0";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
  4.0.0

  org.thejarbar
  facelets-dep
  1.0
  pom

  
  
  
  com.sun.faces
  jsf-api
  2.0.3
  compile
  
  
  com.sun.faces
  jsf-impl
  2.0.3
  compile
  
  
  



I was under the impression that the two are identical?


You should add import. Just having the dependency means
it's available at compile time which is not of any help to you.

Note, though, that scope import is quite limited. It only works in the
dependencyManagement section. See
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html. 



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Strange potential bug Maven2?

2011-05-28 Thread Yucca Nel

Sorry, I will try be clearer... this:


   com.sun.faces
   jsf-api
   2.0.3
   compile
   
   
   com.sun.faces
   jsf-impl
   2.0.3
   compile
   

Is not the same as this:


   org.thejarbar
   hib-jsf-jta-dep
   pom
   1.0
   
===
The pom project:
===

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>

   4.0.0

   org.thejarbar
   facelets-dep
   1.0
   pom

   
   
   
   com.sun.faces
   jsf-api
   2.0.3
   compile
   
   
   com.sun.faces
   jsf-impl
   2.0.3
   compile
   
   
   



I was under the impression that the two are identical?

-Original Message- 
From: Yucca Nel

Sent: Saturday, May 28, 2011 3:29 PM
To: users@maven.apache.org
Subject: Strange potential bug Maven2?

Hello I am having an issue using the following setup:

IDEA 9.03
JDK 6.0.24
Maven 2
Tomcat 7.05

Basically I create a pom project for the sole purpose as a plugin dependency 
for my faces 2 (I plan on having 2 different such projects for JEE and plain 
servlet containers respectively.
I am running a sample project successfully using the following pom from the 
CLI (command: mvn package tomcat:deploy) with my project configured to use a 
local tomcat instance.

At this point everything works, but removing/refactoring the following:



   com.sun.faces
   jsf-api
   2.0.3
   compile
   
   
   com.sun.faces
   jsf-impl
   2.0.3
   compile
   
===

From:

http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>

   4.0.0
   org.jarbar.the
   Jerel-Baker
   war
   1.0-SNAPSHOT
   Jerel-Baker
   http://thejarbar.org/JerelBaker
   
   
   junit
   junit
   3.8.1
   test
   

   
   com.sun.faces
   jsf-api
   2.0.3
   compile
   
   
   com.sun.faces
   jsf-impl
   2.0.3
   compile
   
   
   
   Jerel-Baker
   
   
   
   org.codehaus.mojo
   tomcat-maven-plugin
   
   http://localhost:8080/manager/text
   local_tomcat
   /${project.build.finalName}
   
   
   
   org.apache.maven.plugins
   maven-compiler-plugin
   2.3.1
   
   1.6
   1.6
   
   
   
   
   

===
Into it’s own pom project and then installing it to local repo and then 
including that pom project as a depandancy,

causes failure when accessing the project in browser.

Something along the lines of duplicate TLD, but this tomcat it seems!

I look at my WEB-INF/lib and I see duplicate jsf-api and jsf-impl jars which 
I suspect is causing this.
Is there a reason why I am getting these duplicate jars that don’t 
match(versions)?


Another thing that is worth noting is that the FacesServlet is not found in 
classpath as is evident in IDEA but I am using exact same dependencies and 
only putting them into own pom project!

Is it IDEA or maven?

I can do a youtube video if this is not clear 



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Strange potential bug Maven2?

2011-05-28 Thread Yucca Nel
Hello I am having an issue using the following setup:

IDEA 9.03
JDK 6.0.24
Maven 2
Tomcat 7.05

Basically I create a pom project for the sole purpose as a plugin dependency 
for my faces 2 (I plan on having 2 different such projects for JEE and plain 
servlet containers respectively.
I am running a sample project successfully using the following pom from the CLI 
(command: mvn package tomcat:deploy) with my project configured to use a local 
tomcat instance.
At this point everything works, but removing/refactoring the following:



com.sun.faces
jsf-api
2.0.3
compile


com.sun.faces
jsf-impl
2.0.3
compile

===

From:

http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.jarbar.the
Jerel-Baker
war
1.0-SNAPSHOT
Jerel-Baker
http://thejarbar.org/JerelBaker


junit
junit
3.8.1
test



com.sun.faces
jsf-api
2.0.3
compile


com.sun.faces
jsf-impl
2.0.3
compile



Jerel-Baker



org.codehaus.mojo
tomcat-maven-plugin

http://localhost:8080/manager/text
local_tomcat
/${project.build.finalName}
   


org.apache.maven.plugins
maven-compiler-plugin
2.3.1

1.6
1.6






===
Into it’s own pom project and then installing it to local repo and then 
including that pom project as a depandancy,
causes failure when accessing the project in browser.

Something along the lines of duplicate TLD, but this tomcat it seems!

I look at my WEB-INF/lib and I see duplicate jsf-api and jsf-impl jars which I 
suspect is causing this. 
Is there a reason why I am getting these duplicate jars that don’t 
match(versions)?

Another thing that is worth noting is that the FacesServlet is not found in 
classpath as is evident in IDEA but I am using exact same dependencies and only 
putting them into own pom project!
Is it IDEA or maven?

I can do a youtube video if this is not clear

New to maven and loving it :) Need a little help please...

2010-03-12 Thread Yucca Nel
Hello, google has helped me fantastically up to now and I am in a little need 
of further info.

I am in the process of changing my development environment (JEE5 + JEE6) and 
have started to utilise Maven. I am looking for a xml pom snippet that can help 
me deploy directly to Jboss6 or glassfish v3 when building my pom. If no 
solution exists, I am open to trying geronimo in the hope of better integration 
with maven.