Hi This pom was not deployed using maven deploy command. Instead a hard copy was done, so the user matzew is the only one with enough permissions to make the change. Matthias, could you give me a hand with this one?.
In future releases, the preferred way to publish artifacts should be use this command: mvn clean deploy -DaltDeploymentRepository=myfaces-staging::default::scpexe://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository -Psign-artifacts -DperformRelease=true -Dpassphrase=??? Or update permissions to 775 and 664 regards, Leonardo Uribe 2010/6/10 Leonardo Uribe <[email protected]> > Hi > > Myfaces master pom v7 has a snapshot dependency here: > > <build> > <defaultGoal>install</defaultGoal> > > <plugins> > <plugin> > <artifactId>maven-checkstyle-plugin</artifactId> > > <version>2.2</version> > <dependencies> > <dependency> > <groupId>org.apache.myfaces.buildtools</groupId> > <artifactId>checkstyle-rules</artifactId> > > <version>2-SNAPSHOT</version> > </dependency> > </dependencies> > </plugin> > </plugins> > > > That's bad, really bad. I notice this problem when I tried to compile core > 2.0 branch. The problem we have is myfaces core 2.0.0 artifacts depends from > this pom. In theory we should not change released artifacts, but in this > case I think we should fix it. If by some reason the snapshot repo is down, > people will not be able to compile core 2.0.0 correctly. > > I'll fix it asap because it is necessary that pom to release myfaces core > 2.0.1 > > regards, > > Leonardo Uribe >
