Hi,
On 12/4/06, wendy Lee <[EMAIL PROTECTED]> wrote:
and now I can build it .I don't know if it is a small flaw in the
pom.xmlunder jackrabbit-core
...
org.apache.jackrabbit
jackrabbit-commons
${pom.version}
-
and now I can build it .I don't know if it is a small flaw in the
pom.xmlunder jackrabbit-core
...
org.apache.jackrabbit
jackrabbit-commons
${pom.version}
I modify it to this.
org.apache.jackrabbit
ja
Hi,
On 12/4/06, wendy Lee <[EMAIL PROTECTED]> wrote:
I checkout the jackrabbit-api
&jackrabbit-jcr-commons&jackrabbit-core&jackrabbit-jcr-tests separately and
under each directory I use command "mvn install" ,at last under the
directory of jackrabbit-core .when I use mvn install .
[...]
Reason:
I checkout the jackrabbit-api
&jackrabbit-jcr-commons&jackrabbit-core&jackrabbit-jcr-tests separately and
under each directory I use command "mvn install" ,at last under the
directory of jackrabbit-core .when I use mvn install .
[INFO]
-
I not familiar with maven ..At primary I use maven 1.0.2 ,Now I update it to
2.0.4 .and follow your description , I change my local url to
"/trunk/jackrabbit-core" ( I worked in the /trunk/jackrabbit ) . I update
my directory and found the test codes remove from my local directory . Now I
want t
hI,
On 11/30/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
I'm planning to go forward with the folder renames and other
restructurings outlined in JCR-612 during the weekend.
The restructuring is now done, see JCR-612 and the associated svn
commits for the gory details. During the same process
Hi,
I'm planning to go forward with the folder renames and other
restructurings outlined in JCR-612 during the weekend. This will
likely invalidate existing working copies so you'll need to either
"svn switch" your copies or get clean checkouts before continuing work
on the Jackrabbit sources.
I
