Thank you Martin and Igor, I've learnt a bit more of Git today :-)!
Hi Andrea,
I forgot /pom.xml with the dependencyManagement for this dependency
but later Sven fixed it:
http://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commit;h=0febdc400d2b70c9f15f340bead0093d753ab0e4
The bui
Hi Andrea,
I forgot /pom.xml with the dependencyManagement for this dependency
but later Sven fixed it:
http://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commit;h=0febdc400d2b70c9f15f340bead0093d753ab0e4
The build is OK now - locally, Jenkins and BuildBot
(http://ci.apache.org/bui
Doh!...I get the same error working with Subversion repository. The
exception is complaining of missing version of inject.jar:
Validation Messages:
[0] 'dependencies.dependency.version' is missing for
javax.inject:javax.inject:jar
Does anybody have the same problem and know how to solve
make sure you are on the master branch - that is wicket 6.0
-igor
On Thu, Dec 22, 2011 at 1:15 PM, Andrea Del Bene wrote:
> I've cloned the given repository, but I get the following exception running
> maven:
>
> org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for
> proj
On Thu, Dec 22, 2011 at 10:57 AM, Bertrand Guay-Paquet
wrote:
> With the move to Git, should user-contributed patches be provided using pull
> requests instead of patches in JIRA?
i think until we have the github workflow worked out and documented it
will be easier to stick with patches in jira.
I've cloned the given repository, but I get the following exception
running maven:
org.apache.maven.reactor.MavenExecutionException: Failed to validate POM
for project org.apache.wicket:wicket-ioc at
/home/andrea/WicketBuild/wicket/wicket-ioc/pom.xml
The other Wicket modules seem to work fin
With the move to Git, should user-contributed patches be provided using
pull requests instead of patches in JIRA?
Also, with SVN it was possible to view the changes related to an issue
in the "subversion commits" tab of JIRA. Will it be possible to have
this information with Git?
Bertrand
O
On Wed, Dec 21, 2011 at 8:40 PM, Johan Compagner wrote:
> hmm i use EGit but some how i always get "not authorized" if i try to push
> something
> I am quite sure the username/password is correct, but will recheck it, i
> use this url:
>
> https://jcompag...@git-wip-us.apache.org/repos/asf/wicket.
On Wed, Dec 21, 2011 at 1:40 PM, Johan Compagner wrote:
> hmm i use EGit but some how i always get "not authorized" if i try to push
> something
> I am quite sure the username/password is correct, but will recheck it, i
> use this url:
>
> https://jcompag...@git-wip-us.apache.org/repos/asf/wicket.
hmm i use EGit but some how i always get "not authorized" if i try to push
something
I am quite sure the username/password is correct, but will recheck it, i
use this url:
https://jcompag...@git-wip-us.apache.org/repos/asf/wicket.git
On Wed, Dec 21, 2011 at 19:26, Jeremy Thomerson
wrote:
> On
On Tue, Dec 20, 2011 at 11:46 PM, Jeremy Thomerson <
jer...@wickettraining.com> wrote:
>
> On Tue, Dec 20, 2011 at 11:20 PM, Clint Checketts wrote:
>
>> Jeremy,
>>
>> Will Git development mimic the current subversion workflow, or will we see
>> we see a more Git-ish way like 'git flow'? See-
>> ht
also note that for some clones "trunk" is still the default branch. be
sure to 'git checkout master' which is where 6.0 stuff lives.
-igor
On Wed, Dec 21, 2011 at 8:30 AM, Martin Grigorov wrote:
> On Wed, Dec 21, 2011 at 6:26 PM, Igor Vaynberg
> wrote:
>> not sure if git://git.apache.org/wicke
On Wed, Dec 21, 2011 at 6:26 PM, Igor Vaynberg wrote:
> not sure if git://git.apache.org/wicket.git is kept up with commits to
> git-wip-us
This is what one of the INFRA members said but later we realized that
these mirrors doesn't work at the moment against WIP repo.
Users can use http://git
i think for users its fine to git clone
https://git-wip-us.apache.org/repos/asf/wicket.git
-igor
On Wed, Dec 21, 2011 at 8:26 AM, Igor Vaynberg wrote:
> not sure if git://git.apache.org/wicket.git is kept up with commits to
> git-wip-us
>
> i think for users
>
> On Wed, Dec 21, 2011 at 1:04
not sure if git://git.apache.org/wicket.git is kept up with commits to
git-wip-us
i think for users
On Wed, Dec 21, 2011 at 1:04 AM, Martin Grigorov wrote:
> The most important info is missing - the checkout url! :-)
>
> For devs:
> https://your_apache_usern...@git-wip-us.apache.org/repos/as
On Wed, Dec 21, 2011 at 10:04 AM, Martin Grigorov wrote:
> The most important info is missing - the checkout url! :-)
>
> For devs:
> https://your_apache_usern...@git-wip-us.apache.org/repos/asf/wicket.git
If you set up the .netrc like the git @ apache document states, you
should not provide your
The most important info is missing - the checkout url! :-)
For devs:
https://your_apache_usern...@git-wip-us.apache.org/repos/asf/wicket.git
For users:
git://git.apache.org/wicket.git
or
https://github.com/apache/wicket
On Wed, Dec 21, 2011 at 6:46 AM, Jeremy Thomerson
wrote:
> On Tue, Dec 20,
On Tue, Dec 20, 2011 at 11:20 PM, Clint Checketts wrote:
> Jeremy,
>
> Will Git development mimic the current subversion workflow, or will we see
> we see a more Git-ish way like 'git flow'? See-
> http://nvie.com/posts/a-successful-git-branching-model/
I think at least the core developers are a
renamed trunk to master and set master as repo's default branch
-igor
On Tue, Dec 20, 2011 at 8:04 PM, Jeremy Thomerson
wrote:
> Our SVN repository is now set read-only. For information about getting
> started with Git @ ASF, see [1]. The JIRA issue where we were converted is
> [2].
>
> Unfort
Jeremy,
Will Git development mimic the current subversion workflow, or will we see
we see a more Git-ish way like 'git flow'? See-
http://nvie.com/posts/a-successful-git-branching-model/
I realize that likely the answer is 'we don't know yet', so I'd like to get
the conversation going.
-Clint
O
20 matches
Mail list logo
