mirror of https://github.com/apache/maven.git
Start adding some comments
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162517 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
pdonald
parent
f8d8348e81
commit
4fa0df7855
|
|
@ -9,9 +9,26 @@ of these would help I think.
|
|||
|
||||
- Being able to write artifact handler that would operate to install an
|
||||
xdoclet plugin correctly when an xdoclet plugin is stated as a dependency.
|
||||
* Maybe this pattern could be generalized so you could register arbitrary
|
||||
ArtifactInterceptors (possibly a DAG of them) that will be called to handle
|
||||
events and operations on artifacts. They could even be used to actually
|
||||
implement the operation (ie have a interceptor actually fetch the artifact
|
||||
on request). This is basically an expansion of handler system as it stands
|
||||
so you can add more context and generalize how artifact operations are
|
||||
handled. (PD)
|
||||
|
||||
- With Maven installed it should be a simple command that allows you to
|
||||
checkout the sources for a project.
|
||||
* Maybe this could be generalized so that if you reference a remote
|
||||
descriptor it will download the project. Something like
|
||||
|
||||
$ maven --project http://www.realityforge.org/daedalus-project.xml
|
||||
|
||||
would result in download of project either from remote location or
|
||||
maybe from scm declarations in project descriptor.
|
||||
|
||||
As part of this remote downloading though the user may be asked for
|
||||
input of particular configuration data (ie username etc). (PD)
|
||||
|
||||
- Unified source directory structure that is analagous to the repository
|
||||
itself. This way locations of intermediary artifacts of a build would be
|
||||
|
|
@ -19,20 +36,22 @@ in a known location. This would also help with developer setup i.e. getting
|
|||
new developers up and running. They could run a maven command and have all
|
||||
their source trees set up in the same way as their collegues.
|
||||
|
||||
- I would like to be able to execute some goals (like 'clean') even when
|
||||
not all dependencies are satisfied
|
||||
- I would like to be able to execute some goals (like 'clean') even when
|
||||
not all dependencies are satisfied.
|
||||
* hell yes!!!! Maybe dependency resolution could be a plugin that
|
||||
other plugins depend upon (PD)
|
||||
|
||||
- Support for transitive and group dependencies
|
||||
|
||||
- It should be easy to create a single report without a need to (call like it has place now)
|
||||
maven:site. It will be nice if report generators can produce docs in few diffrent formats
|
||||
(e.g pdf, html, rtf) and this format can be also choosen for group of reports.
|
||||
|
||||
|
||||
- groupId
|
||||
- Let's assume that there exists an artifact type "web-component"
|
||||
- Let's assume that there exists an artifact type "web-component"
|
||||
which is a zip file containg css/js/gifs/jpegs etc
|
||||
Example of such artifact is for example distribution of tigris style.
|
||||
|
||||
|
||||
Say an user has declared the following dependency:
|
||||
|
||||
<depenedency>
|
||||
|
|
@ -41,52 +60,52 @@ their source trees set up in the same way as their collegues.
|
|||
<type>web-component</type>
|
||||
<version>2.0</version>
|
||||
</depenedency>
|
||||
|
||||
|
||||
A dependency of this type should be processed only when users assembles the web application
|
||||
(war:webapp goal in maven-old)
|
||||
|
||||
In short: user can be able to declare goal decorators and goals should be fine-grained
|
||||
|
||||
|
||||
In short: user can be able to declare goal decorators and goals should be fine-grained
|
||||
|
||||
|
||||
- Maven is Java Build Tool. It should be well defined what does it mean to "build java project".
|
||||
It means that stages of the process should be well defined.
|
||||
|
||||
|
||||
pre-compile (this is when tools like JAXB, XDoclet)
|
||||
compile (javac, aspectj)
|
||||
post-compile (aspectj? )
|
||||
post-compile (aspectj? )
|
||||
pre-jar
|
||||
...
|
||||
etc
|
||||
|
||||
It should e.g be possible to use Castor, JAXB plugin, XDoclet plugin without writing a single line
|
||||
of build script. In the ideal case it should be just enough to plug-in XDoclet into process simply
|
||||
by "checking the checkbox in IDE".
|
||||
This is someting what Vincent Massol started in maven-caller plugin. It will be nice to explore this idea.
|
||||
|
||||
|
||||
It should e.g be possible to use Castor, JAXB plugin, XDoclet plugin without writing a single line
|
||||
of build script. In the ideal case it should be just enough to plug-in XDoclet into process simply
|
||||
by "checking the checkbox in IDE".
|
||||
This is someting what Vincent Massol started in maven-caller plugin. It will be nice to explore this idea.
|
||||
|
||||
- Reorganization of repository layout - are we going to map groupId : "a.b.c.d" to path "a/b/c/d"?
|
||||
Are there some better alternatives?
|
||||
|
||||
|
||||
- (Michal) I have tried to implement "platform dependend dependecies".
|
||||
|
||||
|
||||
<depenedency>
|
||||
<groupId>a</groupId>
|
||||
<artifactId>b</artifactId>
|
||||
<type>native</type>
|
||||
<version>2.0</version>
|
||||
</depenedency>
|
||||
|
||||
is resolved as
|
||||
|
||||
</depenedency>
|
||||
|
||||
is resolved as
|
||||
|
||||
a/b-2.0.dll (on windows) or a/b-2.0.so (unix)
|
||||
|
||||
|
||||
Maybe it can/should be done differently?
|
||||
|
||||
|
||||
Maybe it can/should be done differently?
|
||||
What other "platform depended" artifact type do we have?
|
||||
exe? shell-script?
|
||||
|
||||
|
||||
|
||||
|
||||
- how to declare a dependency on JDK and what are possible implications of such dependency
|
||||
(e.g javac/javadoc target jdk)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue