You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Matt Raible (JIRA)" <ji...@codehaus.org> on 2006/02/11 17:05:47 UTC
[jira] Created: (MEV-331) Please upload Acegi Security 1.0.0 RC2
Please upload Acegi Security 1.0.0 RC2
--------------------------------------
Key: MEV-331
URL: http://jira.codehaus.org/browse/MEV-331
Project: Maven Evangelism
Type: Wish
Reporter: Matt Raible
Since this project already uses Maven, and has pom.xml's in it's source tree - creating a bundle should be trivial. Also, it'd be great if the pom.xml recognized that I have spring (the main one) in my pom.xml and didn't download all the smaller spring JARs. I believe 1.0.0 RC2 requires Spring 2.0 M2 (MEV-326).
Is there anyway to expidite the process of getting these uploaded? I can create my own repo for public consumption, but I know you guys discourage that.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MEV-331) Please upload Acegi Security 1.0.0 RC2
Posted by "Matt Raible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-331?page=comments#action_58432 ]
Matt Raible commented on MEV-331:
---------------------------------
Dream:
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>2.0-m1</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-hibernate3</artifactId>
<version>2.0-m1</version>
</dependency>
<!-- To upgrade Hibernate to latest release release -->
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.1.2</version>
</dependency>
<dependency>
<groupId>org.acegisecurity</groupId>
<artifactId>acegi-security</artifactId>
<version>1.0.0-RC1</version>
</dependency>
Willing to live with b/c I doubt Spring is going to specify Geronimo vs. JTA as a dependency:
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>2.0-m1</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-hibernate3</artifactId>
<version>2.0-m1</version>
<exclusions>
<exclusion>
<groupId>javax.transaction</groupId>
<artifactId>jta</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<dependency>
<groupId>geronimo-spec</groupId>
<artifactId>geronimo-spec-jta</artifactId>
<version>1.0.1B-rc4</version>
</dependency>
<!-- To upgrade Hibernate to latest release release -->
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.1.2</version>
</dependency>
<dependency>
<groupId>org.acegisecurity</groupId>
<artifactId>acegi-security</artifactId>
<version>1.0.0-RC1</version>
</dependency>
Reality:
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>2.0-m1</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-hibernate3</artifactId>
<version>2.0-m1</version>
<exclusions>
<exclusion>
<groupId>javax.persistence</groupId>
<artifactId>ejb</artifactId>
</exclusion>
<exclusion>
<groupId>javax.transaction</groupId>
<artifactId>jta</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-mock</artifactId>
<version>2.0-m1</version>
<scope>test</scope>
</dependency>
<!-- To upgrade Hibernate to latest release release -->
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.1.2</version>
</dependency>
<dependency>
<groupId>geronimo-spec</groupId>
<artifactId>geronimo-spec-jta</artifactId>
<version>1.0.1B-rc4</version>
</dependency>
<dependency>
<groupId>org.acegisecurity</groupId>
<artifactId>acegi-security</artifactId>
<version>1.0.0-RC1</version>
<exclusions>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-remoting</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-dao</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-support</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-jdbc</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-web</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
</exclusion>
</exclusions>
</dependency>
Ugh. ;-)
> Please upload Acegi Security 1.0.0 RC2
> --------------------------------------
>
> Key: MEV-331
> URL: http://jira.codehaus.org/browse/MEV-331
> Project: Maven Evangelism
> Type: Wish
> Reporter: Matt Raible
>
>
> Since this project already uses Maven, and has pom.xml's in it's source tree - creating a bundle should be trivial. Also, it'd be great if the pom.xml recognized that I have spring (the main one) in my pom.xml and didn't download all the smaller spring JARs. I believe 1.0.0 RC2 requires Spring 2.0 M2 (MEV-326).
> Is there anyway to expidite the process of getting these uploaded? I can create my own repo for public consumption, but I know you guys discourage that.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MEV-331) Please upload Acegi Security 1.0.0 RC2
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-331?page=comments#action_58433 ]
Carlos Sanchez commented on MEV-331:
------------------------------------
I'm taking a look but poms in cvs need to be in sync to m1 poms (the official build), so it'll take some time
You can put them in your repo under org.appfuse with the poms you want (the ones from previous version + changes) temporary.
You know that you should use the smaller jars, furthermore spring removed stuff from spring.jar in 2.0 ;)
> Please upload Acegi Security 1.0.0 RC2
> --------------------------------------
>
> Key: MEV-331
> URL: http://jira.codehaus.org/browse/MEV-331
> Project: Maven Evangelism
> Type: Wish
> Reporter: Matt Raible
>
>
> Since this project already uses Maven, and has pom.xml's in it's source tree - creating a bundle should be trivial. Also, it'd be great if the pom.xml recognized that I have spring (the main one) in my pom.xml and didn't download all the smaller spring JARs. I believe 1.0.0 RC2 requires Spring 2.0 M2 (MEV-326).
> Is there anyway to expidite the process of getting these uploaded? I can create my own repo for public consumption, but I know you guys discourage that.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org