You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "John Ferguson Smart (JIRA)" <ta...@jakarta.apache.org> on 2005/11/22 11:51:43 UTC

[jira] Created: (TAPESTRY-771) Dependencies are not loaded from Ibiblio when using Tapestry in a Maven 2 project

Dependencies are not loaded from Ibiblio when using Tapestry in a Maven 2 project
---------------------------------------------------------------------------------

         Key: TAPESTRY-771
         URL: http://issues.apache.org/jira/browse/TAPESTRY-771
     Project: Tapestry
        Type: Bug
    Versions: 4.0    
 Environment: Building a Tapestry project with Maven 2 (linux, JDK1.5, Tapestry 4.0-beta-13)
    Reporter: John Ferguson Smart
    Priority: Minor


When using Tapestry in a Maven 2 project, the dependencies are not automatically loaded, so you have to declare them all in the pom.xml, which sort of defeats the purpose of transitive dependency management ;). On Ibiblio (http://www.ibiblio.org/maven2/tapestry/tapestry/4.0-beta-13/), the tapestry-4.0-beta-13.pom looks like this:

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>tapestry</groupId>
  <artifactId>tapestry</artifactId>
  <version>4.0-beta-13</version>
</project>

I suspect it should look like this:

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>tapestry</groupId>
  <artifactId>tapestry</artifactId>
  <version>4.0-beta-13</version>
  <dependencies>
    <dependency>
      <groupId>commons-codec</groupId>
      <artifactId>commons-codec</artifactId>
      <version>1.3</version>
    </dependency>
    <dependency>
      <groupId>commons-fileupload</groupId>
      <artifactId>commons-fileupload</artifactId>
      <version>1.0</version>
    </dependency>
    <dependency>
      <groupId>commons-logging</groupId>
      <artifactId>commons-logging</artifactId>
      <version>1.0.4</version>
    </dependency>
    <dependency>
      <groupId>hivemind</groupId>
      <artifactId>hivemind</artifactId>
      <version>1.1</version>
    </dependency>
    <dependency>
      <groupId>hivemind</groupId>
      <artifactId>hivemind-lib</artifactId>
      <version>1.1</version>
    </dependency>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>javassist</groupId>
      <artifactId>javassist</artifactId>
      <version>3.0</version>
    </dependency>
    <dependency>
      <groupId>oro</groupId>
      <artifactId>oro</artifactId>
      <version>2.0.8</version>
    </dependency>
    <dependency>
      <groupId>ognl</groupId>
      <artifactId>ognl</artifactId>
      <version>2.6.7</version>
    </dependency>
  </dependencies>
</project>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Updated: (TAPESTRY-771) Dependencies are not loaded from Ibiblio when using Tapestry in a Maven 2 project

Posted by "Brian K. Wallace (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-771?page=all ]

Brian K. Wallace updated TAPESTRY-771:
--------------------------------------

    Component: Build

> Dependencies are not loaded from Ibiblio when using Tapestry in a Maven 2 project
> ---------------------------------------------------------------------------------
>
>          Key: TAPESTRY-771
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-771
>      Project: Tapestry
>         Type: Bug

>   Components: Build
>     Versions: 4.0
>  Environment: Building a Tapestry project with Maven 2 (linux, JDK1.5, Tapestry 4.0-beta-13)
>     Reporter: John Ferguson Smart
>     Priority: Minor

>
> When using Tapestry in a Maven 2 project, the dependencies are not automatically loaded, so you have to declare them all in the pom.xml, which sort of defeats the purpose of transitive dependency management ;). On Ibiblio (http://www.ibiblio.org/maven2/tapestry/tapestry/4.0-beta-13/), the tapestry-4.0-beta-13.pom looks like this:
> <project>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>tapestry</groupId>
>   <artifactId>tapestry</artifactId>
>   <version>4.0-beta-13</version>
> </project>
> I suspect it should look like this:
> <project>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>tapestry</groupId>
>   <artifactId>tapestry</artifactId>
>   <version>4.0-beta-13</version>
>   <dependencies>
>     <dependency>
>       <groupId>commons-codec</groupId>
>       <artifactId>commons-codec</artifactId>
>       <version>1.3</version>
>     </dependency>
>     <dependency>
>       <groupId>commons-fileupload</groupId>
>       <artifactId>commons-fileupload</artifactId>
>       <version>1.0</version>
>     </dependency>
>     <dependency>
>       <groupId>commons-logging</groupId>
>       <artifactId>commons-logging</artifactId>
>       <version>1.0.4</version>
>     </dependency>
>     <dependency>
>       <groupId>hivemind</groupId>
>       <artifactId>hivemind</artifactId>
>       <version>1.1</version>
>     </dependency>
>     <dependency>
>       <groupId>hivemind</groupId>
>       <artifactId>hivemind-lib</artifactId>
>       <version>1.1</version>
>     </dependency>
>     <dependency>
>       <groupId>junit</groupId>
>       <artifactId>junit</artifactId>
>       <version>3.8.1</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>javassist</groupId>
>       <artifactId>javassist</artifactId>
>       <version>3.0</version>
>     </dependency>
>     <dependency>
>       <groupId>oro</groupId>
>       <artifactId>oro</artifactId>
>       <version>2.0.8</version>
>     </dependency>
>     <dependency>
>       <groupId>ognl</groupId>
>       <artifactId>ognl</artifactId>
>       <version>2.6.7</version>
>     </dependency>
>   </dependencies>
> </project>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Resolved: (TAPESTRY-771) Dependencies are not loaded from Ibiblio when using Tapestry in a Maven 2 project

Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-771?page=all ]
     
Andreas Andreou resolved TAPESTRY-771:
--------------------------------------

    Fix Version: 4.0.3
     Resolution: Won't Fix

Use 4.0 or 4.0.1. Also see http://issues.apache.org/jira/browse/TAPESTRY-914

> Dependencies are not loaded from Ibiblio when using Tapestry in a Maven 2 project
> ---------------------------------------------------------------------------------
>
>          Key: TAPESTRY-771
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-771
>      Project: Tapestry
>         Type: Bug

>   Components: Build
>     Versions: 4.0
>  Environment: Building a Tapestry project with Maven 2 (linux, JDK1.5, Tapestry 4.0-beta-13)
>     Reporter: John Ferguson Smart
>     Priority: Minor
>      Fix For: 4.0.3

>
> When using Tapestry in a Maven 2 project, the dependencies are not automatically loaded, so you have to declare them all in the pom.xml, which sort of defeats the purpose of transitive dependency management ;). On Ibiblio (http://www.ibiblio.org/maven2/tapestry/tapestry/4.0-beta-13/), the tapestry-4.0-beta-13.pom looks like this:
> <project>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>tapestry</groupId>
>   <artifactId>tapestry</artifactId>
>   <version>4.0-beta-13</version>
> </project>
> I suspect it should look like this:
> <project>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>tapestry</groupId>
>   <artifactId>tapestry</artifactId>
>   <version>4.0-beta-13</version>
>   <dependencies>
>     <dependency>
>       <groupId>commons-codec</groupId>
>       <artifactId>commons-codec</artifactId>
>       <version>1.3</version>
>     </dependency>
>     <dependency>
>       <groupId>commons-fileupload</groupId>
>       <artifactId>commons-fileupload</artifactId>
>       <version>1.0</version>
>     </dependency>
>     <dependency>
>       <groupId>commons-logging</groupId>
>       <artifactId>commons-logging</artifactId>
>       <version>1.0.4</version>
>     </dependency>
>     <dependency>
>       <groupId>hivemind</groupId>
>       <artifactId>hivemind</artifactId>
>       <version>1.1</version>
>     </dependency>
>     <dependency>
>       <groupId>hivemind</groupId>
>       <artifactId>hivemind-lib</artifactId>
>       <version>1.1</version>
>     </dependency>
>     <dependency>
>       <groupId>junit</groupId>
>       <artifactId>junit</artifactId>
>       <version>3.8.1</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>javassist</groupId>
>       <artifactId>javassist</artifactId>
>       <version>3.0</version>
>     </dependency>
>     <dependency>
>       <groupId>oro</groupId>
>       <artifactId>oro</artifactId>
>       <version>2.0.8</version>
>     </dependency>
>     <dependency>
>       <groupId>ognl</groupId>
>       <artifactId>ognl</artifactId>
>       <version>2.6.7</version>
>     </dependency>
>   </dependencies>
> </project>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org