Hi Altuğ, The project builds fine for me.
After doing a fresh checkout, run the following on the command line: > mvn install If that builds successfully on the command line, but it fails within Netbeans, then it means there is a Netbeans configuration problem. I don't use Netbeans, so I'm afraid I can't help with those questions. - Les On Mon, Aug 31, 2009 at 7:18 PM, Altuğ B. Altıntaş<[email protected]> wrote: > Hi; > > I am using maven 2; I wanted to install shiro but it gives : > > [ERROR]BUILD ERROR > ------------------------------------------------------------------------ > Error building POM (may not be this project's POM). > > > Project ID: null:shiro-all:jar:null > > Reason: Cannot find parent: org.apache.shiro:shiro-root for project: > null:shiro-all:jar:null for project null:shiro-all:jar:null > > What does it mean ? > > > I'm using Netbeans 6.7 + maven 2 > > Thanks. > > > 2009/8/6 Les Hazlewood <[email protected]> >> >> Hi everyone, >> >> We've been cleared to make available our Maven snapshots for anyone >> interested to consume them (but please see the NOTE below before doing >> so). They are available in Apache's Nexus installation: >> >> https://repository.apache.org/ >> >> You can find them under the snapshots repository: >> >> https://repository.apache.org/content/repositories/snapshots/ >> >> You can depend on them from within Maven poms via the following dependency >> XML: >> >> <dependency> >> <groupId>org.apache.shiro</groupId> >> <artifactId>shiro-core</artifactId> >> <version>1.0-incubating-SNAPSHOT</version> >> </dependency> >> >> Other important artifact IDs are: >> >> shiro-web (for web/http application support) >> shiro-spring (Spring support) >> shiro-ehcache (Ehcache support) >> shiro-quartz (Quartz session validation job) >> >> Sources and JavaDoc .jars are also available for all of the above. >> >> Please note that these are only SNAPSHOTs and are 'cutting edge' - use >> them at your own risk. >> >> * NOTE: As a project we have not yet made any Apache releases and the >> SNAPSHOTs are *not* yet considered Apache artifacts - they have not >> cleared the Apache release process. They are only provided for those >> that understand this caveat but who still might wish to access them >> for their own testing and development needs. >> >> Cheers, >> >> Les > > > > -- > Altuğ. >
