It's been over 24 hours and ibiblio still gives me cos and quartz for
Spring.  Is the synchronization process broken? Here's my current pom:

    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring</artifactId>
      <version>1.2.6</version>
    </dependency>
    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-mock</artifactId>
      <version>1.2.6</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <groupId>org.springframework</groupId>
          <artifactId>spring-jdbc</artifactId>
        </exclusion>
        <exclusion>
          <groupId>org.springframework</groupId>
          <artifactId>spring-web</artifactId>
        </exclusion>
      </exclusions>
    </dependency>


On 12/21/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> I've put everything but commons-logging as optional. I think this is
> the last change for spring 1.2.6.
>
> On 12/21/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> > On 12/20/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > Probably it worked because there were no dependencies in them, now
> > > that they are maven tries to download them.
> >
> > The previous poms had dependencies listed as well, except that
> > everything was marked optional (true) since commons-logging is the
> > only thing you need to run Spring.
> >
> > >
> > > I'm putting them as optional in the spring pom (almost everything
> > > should be), but you'll miss a lot of the transitive dependency
> > > features. That's why I really encourage the use of the smaller jars.
> >
> > It appears like there's still a few issues.  Yesterday (Monday), I
> > didn't need to have any exclusions on my Spring dependencies.  Now I
> > have to have a bunch to get the same results.
> >
> >    <dependency>
> >      <groupId>org.springframework</groupId>
> >      <artifactId>spring</artifactId>
> >      <version>1.2.6</version>
> >      <exclusions>
> >        <exclusion>
> >          <groupId>aopalliance</groupId>
> >          <artifactId>aopalliance</artifactId>
> >        </exclusion>
> >        <exclusion>
> >          <groupId>com.servlets</groupId>
> >          <artifactId>cos</artifactId>
> >        </exclusion>
> >        <exclusion>
> >          <groupId>quartz</groupId>
> >          <artifactId>quartz</artifactId>
> >        </exclusion>
> >        <exclusion>
> >          <groupId>xdoclet</groupId>
> >          <artifactId>xjavadoc</artifactId>
> >        </exclusion>
> >      </exclusions>
> >    </dependency>
> >    <dependency>
> >      <groupId>org.springframework</groupId>
> >      <artifactId>spring-mock</artifactId>
> >      <version>1.2.6</version>
> >      <scope>test</scope>
> >      <exclusions>
> >        <exclusion>
> >          <groupId>org.springframework</groupId>
> >          <artifactId>spring-jdbc</artifactId>
> >        </exclusion>
> >        <exclusion>
> >          <groupId>org.springframework</groupId>
> >          <artifactId>spring-web</artifactId>
> >        </exclusion>
> >      </exclusions>
> >    </dependency>
> >
> > Thanks for your help.
> >
> > Matt
> >
> > >
> > > Regards
> > >
> > > On 12/20/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> > > > Unfortunately, this change seems to have hosed everything.  Using
> > > > springframework/spring was working *beautifully* before, and now
> > > > neither works.
> > > >
> > > > required artifacts missing:
> > > >   javax.mail:mail:jar:1.3.2
> > > >   javax.transaction:jta:jar:1.0.1B
> > > >   javax.resource:connector:jar:1.0
> > > >   javax.activation:activation:jar:1.0.2
> > > >
> > > > Is it possible to revert things back to what they were?
> > > >
> > > > Matt
> > > >
> > > > On 12/19/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > > > > Hi,
> > > > >
> > > > > I have the poms for org.springframework 1.2.6 ready and will upload 
> > > > > them soon.
> > > > > The messages you get on springframwork are just warnings because the
> > > > > poms don't yet exist, but should work the same as the
> > > > > org.springframework ones that have minimalistic poms.
> > > > >
> > > > > Regards
> > > > >
> > > > > On 12/19/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> > > > > > I like to follow best practices, and it appears that you (the Maven
> > > > > > Team) would prefer we use "org.springframework" for Spring's 
> > > > > > groupId,
> > > > > > rather than "springframework".
> > > > > >
> > > > > > If I change my pom.xml setting to use "org.springframework" for the
> > > > > > groupId (for spring and spring-mock (v 1.2.6)), I get the following
> > > > > > warning:
> > > > > >
> > > > > > [INFO] [resources:resources]
> > > > > > [INFO] Using default encoding to copy filtered resources.
> > > > > > Downloading: 
> > > > > > http://repo1.maven.org/maven2/org/springframework/spring-mock/1.2.6
> > > > > > /spring-mock-1.2.6.pom
> > > > > > [WARNING] Unable to get resource from repository central 
> > > > > > (http://repo1.maven.org
> > > > > > /maven2)
> > > > > > Downloading: 
> > > > > > http://repo1.maven.org/maven2/org/springframework/spring/1.2.6/spri
> > > > > > ng-1.2.6.pom
> > > > > > [WARNING] Unable to get resource from repository central 
> > > > > > (http://repo1.maven.org
> > > > > > /maven2)
> > > > > >
> > > > > > If I change my groupId to be "springframework", I don't get any
> > > > > > warnings.  It seems like org.springframework is not as up-to-date as
> > > > > > springframework, especially since its directories are missing *.pom
> > > > > > files.
> > > > > >
> > > > > > Any ideas?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Matt
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to